Hi Tom,
Thanks for the PR. How did you make this update. Did you just have Visual Studio re-target the .Net Framework?

Thanks

/E

Hi, Eric,

Thanks for your email!

It was not an easy process. If I simply let Nuget update everything, I
would get lots of build-time errors and warnings. In the end, I found that
it worked well to:
0. Start with an unchanged repo
1. With Visual Studio, manually reconfigure each of the service
projects to target .Net Framework 4.6
2. With Visual Studio, manage Nuget packages for solution
a. Accept all updates except:
Autofac (version conflicts with dependencies)
UWP - the update would build fine, but generate an ugly
warning about a dependency. I never did get to the bottom of that.

Since the time I generated the pull request, the Autofac issue has been
resolved by some newer versions of its dependencies. So, for my private
build, I have upgraded Autofac successfully.

I've tested all the basic functionality: notifications, DocumentDB, IAP,
etc. However, I have not yet spent time learning the in-solution (service
side and app-side) tests, so didn't run those. Any documentation on how to
run the tests and on the general test methodology, BTW? :-)

This is an impressive and helpful application - thanks to you and the team
for producing this!

/Tom

On Tue, Aug 23, 2016 at 2:04 PM, Eric Langland notifications@github.com
wrote:

Hi Tom,
Thanks for the PR. How did you make this update. Did you just have Visual
Studio re-target the .Net Framework?

Thanks

/E

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#31 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARWjPNN7jInM7InAgShazCaLbnmJC9R6ks5qizYtgaJpZM4JgscH
.